Best Practices (1/2)
Why should every form input have a <label>?
    Importance of <label> for Form Inputs

    Every form input should have a `<label>` to ensure accessibility, clarity, and usability. Labels provide a clear, descriptive name for the input, which is essential for all users, especially those using screen readers.

    Key Reasons to Use <label>
    • Screen reader support – `<label>` allows assistive technologies to announce the purpose of the input.
    • Clickable area – Clicking the label focuses the associated input, improving usability.
    • Form clarity – Labels provide context for what data is expected, reducing errors.
    • Keyboard navigation – Helps users navigate forms efficiently using Tab and Shift+Tab.
    • Consistency – Supports standardized accessibility practices across web forms.
    How to Use <label>
    • Associate the label using the `for` attribute pointing to the input's `id`: `<label for="email">Email:</label><input id="email" type="email">`
    • Alternatively, wrap the input inside the label: `<label>Email: <input type="email"></label>`
    • Ensure label text is clear, concise, and descriptive.
    Best Practices
    • Never rely solely on placeholders as labels; they disappear on focus and may not be read by screen readers.
    • Use visible text for labels whenever possible.
    • Combine labels with `aria-describedby` if additional instructions are needed.